Guideline: In More Details - Adjust The Strategy

In many cases, the test strategy needs to be adjusted. A good reason to change the strategy is that certain tests yield far more or less defects than expected, or that the test process shows that the product risks were not estimated correctly or additional product risks are perceived. It may be decided to specify and execute extra tests or execute only part of planned tests or even eliminate them altogether. A less adequate reason to change the strategy is if one wishes to compensate delays in the rest of the development process in costs or time by means of reduced testing.

Using the established strategy as a basis, the test manager consults with the client about the changed risk assessment and which aspects require additional or reduced testing. By indicating what testing will be reduced in relation to the defined product risks, the test manager is able to report correctly on the possibly emerged higher risk that remains after the test.

The table below is a good example of a changed PRA and test strategy at the overall level.

In this example, the allocated risk class for functionality has been increased for subsystem 2 and the total system. However, the test thoroughness in the system test and user acceptance test of subsystem 1 has become lighter (from 3 to 2 and from 2 to 1, symbolised by ○). However, the system test of the total system is intensified, from 1 to 2, symbolised by

. It is clear that the risk increases and the test thoroughness drops. Naturally this requires an explanation as well as a correct risk assessment by the test manager on behalf of the client (not covered by this example).

The most common and expected changes relate to the planning. If replanning one test level has consequences for the planning of other test levels and project parts, all stakeholders are notified and, where necessary, their approval must be obtained.